-
Notifications
You must be signed in to change notification settings - Fork 549
Remove containerPackageInfo
parameter in createOdspCreateContainerRequest
#23872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove containerPackageInfo
parameter in createOdspCreateContainerRequest
#23872
Conversation
containerPackageInfo
parameter in createOdspCreateContainerRequest
containerPackageInfo
parameter in createOdspCreateContainerRequest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
packages/drivers/odsp-driver/src/createOdspCreateContainerRequest.ts:35
- With the removal of the containerPackageInfo parameter and its associated URL fragment, please ensure that any parts of the system relying on containerPackageName being sent through createOdspCreateContainerRequest are updated (for example, by using OdspDriverUrlResolverForShareLink as described).
)}${shareLinkRequestParams ? `&${shareLinkRequestParams}` : ""}`,
packages/drivers/odsp-driver/src/test/odspDriverResolverTest.spec.ts:457
- The removal of the containerPackageInfo parameter led to the deletion of this test case. Please confirm that the new behavior (i.e. setting the container package name via OdspDriverUrlResolverForShareLink) is covered elsewhere in the tests.
it("Should create request with containerPackageName and resolve it", async () => {
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blocking merge only to help with release race-conditions. I'll remove this block once release branch is created.
)}${containerPackageInfo ? `&containerPackageName=${getContainerPackageName(containerPackageInfo)}` : ""}${shareLinkRequestParams ? `&${shareLinkRequestParams}` : ""}`, | ||
)}${shareLinkRequestParams ? `&${shareLinkRequestParams}` : ""}`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking behavioral change. Is there a deprecation PR planned before this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes there is, I'm working on one but I'm having trouble making the deprecation. I'm not sure how to deprecate the parameter within the function.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can't deprecate the parameter, but you can deprecate calling the function with that form. Example:
interface Test {
/** @deprecated */
fn(a: string, b: boolean): void;
fn(a: string): void;
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created deprecation PR: #23919
🔗 Found some broken links! 💔 Run a link check locally to find them. See linkcheck output
|
Description
With PR: #22849 we introduced a parameter for ODSP that will not be used.
Since it is public, we will first mark it as deprecated, and then in the next release remove it. Make sure we inform Loop to not take dependency on it.
This is the follow up task to ensure that the parameter is deleted.
Reviewer Guidance
Please let me know if there's anything that I should change or be aware of. Thanks!
Fixes: AB#31049